Apparatus and Method for Flexible Web Service Deployment

ABSTRACT

An apparatus and method for deploying web services in a web services infrastructure are provided. with the apparatus and method, a deployment descriptor for a web service is retrieved from a configuration file. A location type in the deployment descriptor is provided for identifying whether the web service is implemented using a web services description language (WSDL) document only, a JavaBean only, or both a WSDL document and a JavaBean. Based on the location type, and associated attributes of the location type, processes are performed for generating an internal definition of the web service to thereby deploy the web service in the web services infrastructure. The internal definition may be generated from the WSDL document directly, if the location type is WSDL only. If the location type is JavaBean only, the internal definition may be generated by first generating a WSDL document from the JavaBean and then generating the internal definition from the generated WSDL document. If the location type is both a WSDL document and JavaBean, then the internal definition is generated from the WSDL document with a Java binding being added to reference the JavaBean.

RELATED APPLICATIONS

The present invention is related to similar subject matter of co-pendingand commonly assigned U.S. patent application Ser. No.______ (AttorneyDocket No. AUS920020608US1) entitled “Dynamic Web Service ImplementationDiscovery and Selection Apparatus and Method,” filed on and U.S. patentapplication Ser. No.______ (Attorney Docket No. AUS920020610US1)entitled “Apparatus and Method for Selecting a Web Service in Responseto a Request from a Client Device,” filed on , both of which are herebyincorporated by reference.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention is directed to an apparatus and method of flexibleweb service deployment. More specifically, the present invention isdirected to an apparatus and method for deploying a web service using aweb services description language document, a Java bean, or both.

2. Description of Related Art

In service-oriented architectures, the fundamental premise is the reuseof web services across one or more enterprise applications. Web servicesare services that are offered across the Internet that are built usingstandard technologies that allow interoperability between systems andapplications. Web services are typically invoked by enterpriseapplications to perform some extended functionality not otherwiseavailable in the enterprise application itself. The enterpriseapplications and their associated enterprise systems are often referredto as “clients” of the web services that they invoke.

Web services are described using a standard language called the WebServices Description Language (WSDL). Co-developed by Microsoft and IBM,WSDL describes the protocols and data types used by the web service.WSDL descriptions can be referenced in a Universal Description,Discovery and Integration (UDDI) registry in order to promote the use ofWeb services worldwide. Typically, a web service provider publishesinformation about its web service in a UDDI registry; that informationpoints to the WSDL description of the web service. A client that wantsto use the web service obtains the WSDL from a UDDI registry or perhapsother sources. Using the information in the WSDL document, the clientcan access the web service.

Both the web service provider and the web service client require a “webservices infrastructure.” The provider infrastructure must know aboutthe web services it is to provide. Thus, web services must be “deployed”in such provider infrastructures. There are several examples of providerinfrastructures including Apache SOAP, Apache Axis, or the IBM WebServices Gateway. These infrastructures differ in the requirements fordeploying web services, however. Apache infrastructures supportdeployment simply by naming the “local” implementation, i.e., on thesame node, (in Java, the class name), because the implementation isalways local. The Gateway, however, requires that any implementation bedescribed using WSDL, because the Gateway supports implementations thatcan be local (for example a Java class) or remote, i.e., a web servicerunning on a different node, such that the Gateway is acting as a proxyor intermediary.

A web service implementation may require complex data types asparameters or return values. For convenience, these data types areimplemented as structures, as in the C language, or classes, as inobject-oriented languages such as Java. WSDL supports the description ofdata types of arbitrary complexity. A WSDL description, as an XMLdocument, uses namespace-qualified names (qname) to identify data typesand other entities described in the WSDL document. The data type qnamesmust be used in the SOAP messages that flow between a web service and aclient of that web service to identify instances of parameter and returnvalue types.

When a web service provider deploys a web service into its web serviceinfrastructure, such as Apache SOAP, or Apache Axis, the provider musttell the infrastructure how to match the data types in the SOAP messagewith the actual implementation of the data type used by the web serviceimplementation. Similarly, a web service client that wishes to useimplementations of data types must also tell its infrastructure how tomatch the data types in the SOAP message with the actual implementationof the data type used by the client. This is accomplished in bothinfrastructures by defining a mapping to the infrastructure. The mappingrelates a qname to a structure or class name. The actual data typeimplementations may or may not be the same, and typically they will notbe the same.

Since the data type qname information in the WSDL document used by theclient is generated by the provider of the web service, there is aguaranteed match. That is, the client must include the namespaceinformation for data types from the WSDL document produced by the webservice provider in the messages it sends to the web service, so thatthe web service provider understands how to match the data.

Thus, some known systems require that all web services, either remote orlocal, be described using WSDL. Other known systems allow local servicesto be described using only a name of the implementing class, i.e.described as JavaBeans. There is no known system that facilitates theuse of both WSDL document descriptions for remote and local web servicesand/or local description of web services as JavaBeans.

SUMMARY OF THE INVENTION

In view of the above, it is desirable to have an improved infrastructurethat permits both remote web service implementations and local webservice implementations and to make both implementations available to aclient. However, typically local web service implementations do not haveWSDL documents established for them. In addition, to be competitive withknown infrastructures, such as Apache infrastructures, it is desirable,and much more convenient, to allow deployment of local implementationssimply by identifying the name of the local implementation, such as aJava class, rather than for development of a WSDL document for the localweb service implementation.

In addition, it is also important to support redeployment of local webservices formerly offered by other infrastructures and described byexisting WSDL documents. older infrastructures use qnames, in particularthe namespace component of the qnames, that are unique to thatinfrastructure. Clients of web services deployed in thoseinfrastructures use the qnames from the original WSDL, and so thoseqnames must be maintained in any new WSDL generated. This allowsexisting clients to access web services deployed in the improvedinfrastructure by changing only the endpoint information in the client.This can be achieved by supplying the original WSDL when deploying localweb service implementation in the improved infrastructure.

The present invention provides an apparatus and method for deploying webservices in an improved web services infrastructure, the web servicesbus, such that the web services may be deployed using either localJavaBean representations of the web service and/or web servicedescription language representations of the web service. With theapparatus and method, a deployment descriptor for a web service isretrieved from a configuration file. A location type in the deploymentdescriptor is provided for identifying whether the web service isimplemented using a web services description language (WSDL) documentonly, a JavaBean only, or both a WSDL document and a JavaBean.

Based on the location type, and associated attributes of the locationtype, processes are performed for generating an internal definition ofthe web service to thereby deploy the web service in the web servicesinfrastructure. The internal definition may be generated from the WSDLdocument directly, if the location type is WSDL only. If the locationtype is JavaBean only, the internal definition may be generated by firstgenerating a WSDL document from the JavaBean and then generating theinternal definition from the generated WSDL document. If the locationtype is both a WSDL document and JavaBean, then the internal definitionis generated from the WSDL document with a Java binding being added toreference the JavaBean.

The present invention provides the ability to use both WSDL and aJavaBean. This allows client devices to continue to use the type nameinformation in the existing WSDL, yet invoke services using the bussupporting a JavaBean as the real implementation. The present inventionallows this by creating a description of the service using type nameinformation from the existing WSDL mapped to the actual Java types usedby the JavaBean. This requires the client to change only the actualendpoint information for the service to invoke the JavaBean deployed inthe bus infrastructure instead of the original environment from whichthe existing WSDL was derived.

These and other features and advantages of the present invention will bedescribed in, or will become apparent to those of ordinary skill in theart in view of, the following detailed description of the preferredembodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the invention are setforth in the appended claims. The invention itself, however, as well asa preferred mode of use, further objectives and advantages thereof, willbest be understood by reference to the following detailed description ofan illustrative embodiment when read in conjunction with theaccompanying drawings, wherein:

FIG. 1 is an exemplary block diagram of a distributed data processingsystem in which the present invention may be implemented;

FIG. 2 is an exemplary diagram of a server computing device with whichthe present invention may operate;

FIG. 3 is an exemplary diagram of a client computing device in which thepresent invention may be implemented;

FIG. 4 is an exemplary diagram illustrating a web services “bus”according to the present invention;

FIG. 5 is an exemplary diagram illustrating a configuration file formatin accordance with the present invention;

FIG. 6 is flowchart outlining an exemplary operation of the presentinvention when generating an internal service definition for a webservice implementation;

FIG. 7 is a flowchart outlining an exemplary operation of the presentinvention when generating an internal service definition for a JavaBeanonly web service implementation;

FIG. 8 is a flowchart outlining an exemplary operation of the presentinvention when generating an internal service definition for a JavaBeanand WSDL web service implementation;

FIG. 9 is a flowchart outlining an exemplary operation of the presentinvention when generating a Java binding for a service definition of aweb service implementation;

FIG. 10 is an example signature of an AddressBook JavaBean used toillustrate the results of the present invention;

FIG. 11A is an example of an Address JavaBean used as a parameter by theAddressBook JavaBean of FIG. 10;

FIG. 11B is an example of a PhoneNumber JavaBean used as a field in theAddress JavaBean of FIG. 11A;

FIGS. 12A-12C illustrate an example WSDL document generated for theAddressBook JavaBean using JAVA2WSDL according to the processes of thepresent invention for web services that are described only as aJavaBean;

FIGS. 13A-13C illustrate the internal service description of FIGS.12A-12C after a Java binding has been added to it;

FIGS. 14A-14C illustrate an original WSDL description derived from theAddressBook JavaBean of FIG. 11A according to the processes of thepresent invention for web services that are described by both a WSDLdocument and a JavaBean; and

FIGS. 15A-15C illustrate the WSDL description of FIGS. 14A-14C after aJava binding has been added to it.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

As previously mentioned, the present invention is directed to apparatusand method of flexible web service deployment. More specifically, thepresent invention is directed to an apparatus and method for deploying aweb service using a web services description language document, a Javabean, or both.

It is prudent to first provide a brief description of the environment inwhich the present invention may operate. Thus, FIGS. 1-3 provideexemplary diagrams of the computing network and computing devices inwhich the present invention operates. FIGS. 1-3 are exemplary and areintended to provide a context for the remaining description.

With reference now to the figures, FIG. 1 depicts a pictorialrepresentation of a network of data processing systems in which thepresent invention may be implemented. Network data processing system 100is a network of computers in which the present invention may beimplemented. Network data processing system 100 contains a network 102,which is the medium used to provide communications links between variousdevices and computers connected together within network data processingsystem 100. Network 102 may include connections, such as wire, wirelesscommunication links, or fiber optic cables.

In the depicted example, server 104 is connected to network 102 alongwith storage unit 106. In addition, clients 108, 110, and 112 areconnected to network 102. These clients 108, 110, and 112 may be, forexample, personal computers or network computers. In the depictedexample, server 104 provides data, such as boot files, operating systemimages, and applications to clients 108-112. Clients 108, 110, and 112are clients to server 104. Network data processing system 100 mayinclude additional servers, clients, and other devices not shown.

In the depicted example, network data processing system 100 is theInternet with network 102 representing a worldwide collection ofnetworks and gateways that use the Transmission ControlProtocol/Internet Protocol (TCP/IP) suite of protocols to communicatewith one another. At the heart of the Internet is a backbone ofhigh-speed data communication lines between major nodes or hostcomputers, consisting of thousands of commercial, government,educational and other computer systems that route data and messages. Ofcourse, network data processing system 100 also may be implemented as anumber of different types of networks, such as for example, an intranet,a local area network (LAN), or a wide area network (WAN). FIG. 1 isintended as an example, and not as an architectural limitation for thepresent invention.

Referring to FIG. 2, a block diagram of a data processing system thatmay be implemented as a server, such as server 104 in FIG. 1, isdepicted in accordance with a preferred embodiment of the presentinvention. Data processing system 200 may be a symmetric multiprocessor(SMP) system including a plurality of processors 202 and 204 connectedto system bus 206. Alternatively, a single processor system may beemployed. Also connected to system bus 206 is memory controller/cache208, which provides an interface to local memory 209. I/O bus bridge 210is connected to system bus 206 and provides an interface to I/O bus 212Memory controller/cache 208 and I/O bus bridge 210 may be integrated asdepicted.

Peripheral component interconnect (PCI) bus bridge 214 connected to I/Obus 212 provides an interface to PCI local bus 216. A number of modemsmay be connected to PCI local bus 216. Typical PCI bus implementationswill support four PCI expansion slots or add-in connectors.Communications links to clients 108-112 in FIG. 1 may be providedthrough modem 218 and network adapter 220 connected to PCI local bus 216through add-in boards. Additional PCI bus bridges 222 and 224 provideinterfaces for additional PCI local buses 226 and 228, from whichadditional modems or network adapters may be supported. In this manner,data processing system 200 allows connections to multiple networkcomputers. A memory-mapped graphics adapter 230 and hard disk 232 mayalso be connected to I/O bus 212 as depicted, either directly orindirectly.

Those of ordinary skill in the art will appreciate that the hardwaredepicted in FIG. 2 may vary. For example, other peripheral devices, suchas optical disk drives and the like, also may be used in addition to orin place of the hardware depicted. The depicted example is not meant toimply architectural limitations with respect to the present invention.

The data processing system depicted in FIG. 2 may be, for example, anIBM eServer pSeries system, a product of International Business MachinesCorporation in Armonk, N.Y., running the Advanced Interactive Executive(AIX) operating system or LINUX operating system.

With reference now to FIG. 3, a block diagram illustrating a dataprocessing system is depicted in which the present invention may beimplemented. Data processing system 300 is an example of a clientcomputer. Data processing system 300 employs a peripheral componentinterconnect (PCI) local bus architecture. Although the depicted exampleemploys a PCI bus, other bus architectures such as Accelerated GraphicsPort (AGP) and Industry Standard Architecture (ISA) may be used.Processor 302 and main memory 304 are connected to PCI local bus 306through PCI bridge 308. PCI bridge 308 also may include an integratedmemory controller and cache memory for processor 302. Additionalconnections to PCI local bus 306 may be made through direct componentinterconnection or through add-in boards.

In the depicted example, local area network (LAN) adapter 310, SCSI hostbus adapter 312, and expansion bus interface 314 are connected to PCIlocal bus 306 by direct component connection. In contrast, audio adapter316, graphics adapter 318, and audio/video adapter 319 are connected toPCI local bus 306 by add-in boards inserted into expansion slots.Expansion bus interface 314 provides a connection for a keyboard andmouse adapter 320, modem 322, and additional memory 324. Small computersystem interface (SCSI) host bus adapter 312 provides a connection forhard disk drive 326, tape drive 328, and CD-ROM drive 330. Typical PCIlocal bus implementations will support three or four PCI expansion slotsor add-in connectors.

An operating system runs on processor 302 and is used to coordinate andprovide control of various components within data processing system 300in FIG. 3. The operating system may be a commercially availableoperating system, such as Windows XP, which is available from MicrosoftCorporation. An object oriented programming system such as Java may runin conjunction with the operating system and provide calls to theoperating system from Java programs or applications executing on dataprocessing system 300. “Java” is a trademark of Sun Microsystems, Inc.Instructions for the operating system, the object-oriented operatingsystem, and applications or programs are located on storage devices,such as hard disk drive 326, and may be loaded into main memory 304 forexecution by processor 302.

Those of ordinary skill in the art will appreciate that the hardware inFIG. 3 may vary depending on the implementation. Other internal hardwareor peripheral devices, such as flash read-only memory (ROM), equivalentnonvolatile memory, or optical disk drives and the like, may be used inaddition to or in place of the hardware depicted in FIG. 3. Also, theprocesses of the present invention may be applied to a multiprocessordata processing system.

As another example, data processing system 300 may be a stand-alonesystem configured to be bootable without relying on some type of networkcommunication interfaces As a further example, data processing system300 may be a personal digital assistant (PDA) device, which isconfigured with ROM and/or flash ROM in order to provide non-volatilememory for storing operating system files and/or user-generated data.

The depicted example in FIG. 3 and above-described examples are notmeant to imply architectural limitations. For example, data processingsystem 300 also may be a notebook computer or hand held computer inaddition to taking the form of a PDA. Data processing system 300 alsomay be a kiosk or a Web appliance.

As mentioned above, the present invention provides an improvedinfrastructure that permits both remote web service implementations andlocal web service implementations and to make both implementationsavailable to a client. The improved infrastructure of the presentinvention is implemented in a web services bus. Various aspects of theweb services bus are described in the incorporated U.S. patentapplication Ser. No. ______ (Attorney Docket No. AUS920020608US1)entitled “Dynamic Web Service Implementation Discovery and SelectionApparatus and Method,” and U.S. patent application Ser. No. ______(Attorney Docket No. AUS920020610US1) entitled “Apparatus and Method forSelecting a Web Service in Response to a Request from a Client Device.”A brief overview of the improved infrastructure as well as a descriptionof the implementation of the present invention in this improvedinfrastructure will now be provided.

FIG. 4 is an exemplary diagram illustrating a web services “bus”according to the present invention. With the present invention, on aclient side of the system, a client device 410 is coupled to a network430 via an extended web services infrastructure on-ramp device 420. On aserver side of the system, requests from client devices are receivedover the network 430 via the off-ramp device 440. Target services 460are accessed through the on-ramp device 450 which is used to performdiscovery and selection of target service implementations based on theservice portType implied by of the request from the client device 410.Web services implementations are described to the on-ramp device 450,i.e. deployed by adding their descriptions to the configuration file442, as WSDL documents.

With the present invention, the client device 510 includes one or moreapplications running on the client device 410. These applicationsinterface with the on-ramp device 420 via the application programinterfaces (APIS) 421 that take the operations performed by theapplication requiring a web service and provide operation information tothe engine 422 of the on-ramp device 420 which generates a request for aweb service operation using WSDL service descriptions. The web serviceoperation request is then sent to the off-ramp 440 via the providerinterface(s) 423, network 430 and channels 441.

The off-ramp device 440 receives the request for a web service operationfrom the on-ramp device 420 and checks a configuration file 442 todetermine if the requested web service identified in the WSDL servicedefinition of the request is recognized by the off-ramp device 440. Theconfiguration file 442 contains a listing of the web services that aresupported by the off-ramp device 440. Web services must be deployed inthe off-ramp 440, i.e., their descriptions must be added to theconfiguration file 442, before they can be recognized by the off-ramp440 and used to satisfy web service operation requests from clientdevices. As will be discussed in greater detail hereafter, web servicesmay be deployed with the off-ramp as either web services whoseimplementation is defined by a WSDL document, web services whoseimplementation is a JavaBean, or web services whose implementation is aJavaBean and is also described in a WSDL document.

Web services are identified in the configuration file 442 by theirserviceName. In order to determine if the requested web service is knownto the off-ramp 440, a determination is made as to whether theserviceName identified in the request for a web service operation isfound in the configuration file 442. If the serviceName specified is notin the configuration file 442, the off-ramp returns a fault to theclient.

As shown in FIG. 5, the serviceName in the configuration file 442 has anassociated deployment description that provides a recognizabledescription of how the web service may be deployed in the web servicesinfrastructure. The deployment descriptor contains a location type 510attribute and additional attributes 520 dependent on the value of thelocation type attribute. The location type 510 identifies whether thereal implementation of the web service supporting the correspondingportType is described using WSDL only, implemented as a JavaBean, orboth. The additional attributes 520 provide additional informationnecessary to make use of a specific implementation of the web service.FIG. 5 illustrates the three possible location types and theircorresponding additional attributes in accordance with the presentinvention.

As shown in FIG. 5, a first location type 530 may be a WSDL onlylocation type, e.g., “URL” location type. The attributes 532 for a WSDLonly location type include an identifier of the location of a WSDLdocument that describes the web service implementation. The WSDL onlylocation type is typically used to describe remotely located webservices that are accessible via a remote access protocol, such asSOAP/HTTP.

A second location type 540 for a web service implementation is aJavaBean location type. The attributes 542 for a JavaBean location typeinclude a name of the class of the real implementation of the webservice and a namespace used in a WSDL-based description that isautomatically generated by the present invention to describe the webservice implementation. The JavaBean location type is typically used todeploy local web services.

The third location type 550 for a web service implementation is a “both”location type indicating that the web service is implemented as aJavaBean but is also described in a WSDL document generated by anotherweb service provider infrastructure. The attributes 552 for a locationtype indicating both WSDL and JavaBean implementations include alocation attribute identifying a location of a WSDL document describingthe original web service implementation and a class name identifying thename of a class of the real implementation of the web service.

The description of the web services in the configuration file 442 may begenerated by a human administrator or by an automatic mechanism. Forexample, when a new web service is to be added to the web servicessupported by the off-ramp 540, a registration process, such as providinga web service that can modify the configuration file, may be used toidentify the type of web service implementation, its location, classname, service namespace, and the like. This information may then beformatted and stored in the configuration file 442 for later use inaccessing the new service implementation.

In order for the web service implementation to be accessible via theoff-ramp 440, an internal definition of the web service implementationmust be generated and stored in memory. This internal definition allowsthe off-ramp to quickly access the information needed to invoke the webservice implementation upon a request from a client. In order togenerate an internal definition for a web service implementation, theoff-ramp examines the location type 510 defined in the deploymentdescriptor of the web service in the configuration file 442. If thelocation type indicates that the web service is only described in a WSDLdocument, the off-ramp 440 loads the WSDL document indicated in thelocation attribute 520 and uses a toolkit, such as Web ServicesDescription Language for Java (WSDL4J), to convert the WSDL documentinto an internal definition of the web service implementation. WSDL4J isa known Java toolkit that allows the creation, representation, andmanipulation of WSDL documents describing services. Information aboutWSDL4J may be obtained, for example, fromwww-124.ibm.com/developerworks/projects/wsd14j/.

If the location type indicates that the web service is implemented onlyas a JavaDean, an application for converting from Java to WSDL, such asJAVA2WSDL from the Apache Axis project, is used to first create a WSDLdocument with a SOAP/HTTP binding and corresponding port in a service.From the WSDL document, a WSDL4J definition is created so that thedescription can be manipulated. Thereafter, a Java binding is added tothe definition. Alternatively, other types of applications, such asWebSphere Studio Application Developer version 5, may be used to createthe required Java binding direction from the JavaBean. Both JAVA2WSDLand WebSphere Studio Application Developer version 5 are knownapplications and information about them may be obtained, for example,from www.systinet.com/doc/wasp_jserver/tools/java2WSDL.html andwww-3.ibm.com/software/ad/studioappdev/, respectively.

If the location type of the web service indicates that it is bothimplemented as a JavaBean and described in a WSDL document from anotherweb services provider infrastructure, an internal definition of the webservice is generated from the WSDL document, using for example, theWSDL4J toolkit noted earlier, and a Java binding is added to theinternal definition, with as much information as possible from theoriginal WSDL document being retained, in particular namespaces.

With the present invention, if the off-ramp 440 consults theconfiguration file 442 and determines that the requested servicecorresponds to a web service that has a deployment descriptor indicatingthe web services is only described as a WSDL document, and the WSDLdocument contains a “remote” protocol binding, for example a SOAP/HTTPbinding, the off-ramp 440 acts as an intermediary between the clientdevice and the real implementation of the web service. As anintermediary, the off-ramp passes requests to, and receives responsesfrom, the real implementation of the web service at the endpointidentified in the WSDL document.

If the WSDL document contains a “local” protocol binding, for example, aJava binding, the off-ramp 440 acts as an endpoint by directly invokingthe JavaBean class identified by the WSDL document. Likewise, if theconfiguration file 442 indicates that the requested service correspondsto a web service whose real implementation is a JavaBean, the off-ramp440 directly invokes the JavaBean described in the attributes set forthin the configuration file 442. If the configuration file 442 indicatesthat the requested service corresponds to a web service whose realimplementation is described by a WSDL document and implemented by aJavaBean, the off-ramp 440 directly invokes the JavaBean described inthe attributes set forth in the configuration file.

FIG. 6 is a flowchart outlining an exemplary operation of the presentinvention when generating an internal service definition for a webservice implementation. As shown in FIG. 6, the operation starts byreceiving a request for a web services operation from a client device(step 610). A deployment descriptor corresponding to the web service inthe request received from the client device is then retrieved from theconfiguration file, or in memory version of the configuration file (step620). The location type in the deployment descriptor is then read (step630) and a determination is made as to whether the location type is aWSDL only location type (step 640). If so, the internal definition ofthe web service implementation is generated from the WSDL documentspecified in the location type attributes (step 650). This may be done,for example, by using the WSDL4J toolkit previously discussed.

If the location type is not WSDL only, then a determination is made asto whether the location type is JavaBean only (step 660). If thelocation type is JavaBean only, the internal definition of the webservices implementation is generated from the JavaBean (step 670). Thismay be done, for example, by using the JAVA2WSDL or WebSphere StudioApplication Developer application previously discussed. The details ofstep 670 are shown in FIG. 7, described hereafter.

If the location type is neither WSDL only nor JavaBean only, then thelocation type, in a preferred embodiment of the present invention, mustbe “both,” indicating that the web service implementation is describedin a WSDL document and implemented as a JavaBean. If the location typeis “both”, the internal definition of the web service implementation isgenerated from both the JavaBean and the WSDL document (step 680). Thedetails of step 680 are shown in FIG. 8, discussed hereafter.

It should be noted that, in some implementations of the presentinvention, there may be additional location types in addition to, or inreplacement of, the WSDL only, JavaBean only, and both location typesdescribed herein. In such implementations, additional checks of locationtype may be required in addition to, or in replacement of, the decisionsteps described in FIG. 7.

FIG. 7 is a flowchart outlining an exemplary operation of the presentinvention when generating an internal service definition for a JavaBeanonly web service implementation. As shown in FIG. 7, the operationstarts by generating a WSDL document with a SOAP binding (step 710).This may be done, for example, using the JAVA2WSDL or WebSphere StudioApplication Developer application previously discussed. Thus, the resultof step 710 is a WSDL document describing the web serviceimplementation.

From this WSDL document, an internal definition of the web serviceimplementation is generated (step 720). This may be done, for example,using the WSDL4J toolkit discussed earlier. After the internaldefinition of the web service implementation is generated, a Javabinding is added to the internal definition (step 730). The process ofadding a Java binding to an internal definition of a web serviceimplementation is illustrated in FIG. 9, described herein below.

FIG. 8 is a flowchart outlining an exemplary operation of the presentinvention when generating an internal service definition for a JavaBeanand WSDL document. As shown in FIG. 8, the operation starts withgenerating an internal definition for the web service implementationfrom the WSDL document (step 810). A Java binding corresponding to theJavaBean for this web service implementation is then added to theinternal definition of the web service implementation (step 820) usingthe class name specified in the location type attributes of thedeployment descriptor for this web service implementation.

FIG. 9 is a flowchart outlining an exemplary operation of the presentinvention when generating a Java binding for a service definition of aweb service implementation. As shown in FIG. 9, the operation starts byintrospection of the target JavaBean (step 910). Introspection allows anunderstanding of the methods of the JavaBean (the operations provided bythe web service) and the data types used by the JavaBean as parametersand return values. The data types used by the target JavaBean are thenmapped to the data types defined in the internal definition of the webservice implementation from the WSDL definition (step 920).

The namespaces for Java extensibility elements are then added to theinternal definition (step 930). Thereafter, the existing binding andservice elements in the internal definition are removed (step 940). Forexample, a WSDL document is created from a JavaBean using JAVA2WSDL, aSOAP binding is added to the WSDL document. This SOAP binding is removedduring step 940 so that the internal definition of the web serviceimplementation includes only the Java binding being created.

The Java binding is then added to the internal definition (step 950).This may include adding extensibility elements for mapping to the datatypes used. Thereafter, a new WSDL service element with a port thatreferences the Java binding is added (step 960).

The results of the use of the present invention are illustrated in theexamples shown in FIGS. 10 through 15C. FIG. 10 is an example signatureof an AddressBook JavaBean used to illustrate the results of the presentinvention. FIG. 11A is an example of an Address JavaBean used as aparameter by the AddressBook JavaBean of FIG. 10. FIG. 11B is an exampleof a PhoneNumber JavaBean used as a field in the Address JavaBean ofFIG. 11A. FIGS. 12A-12C and 13A-13C illustrate the results of deployingAddressBook as a local web service implementation with the location typeof “bean.” FIGS. 14A-14C and 15A-15C illustrate the results of deployingan AddressBook JavaBean as a local web service implementation with thelocation type of “both.” FIGS. 12A-12C illustrate an example WSDLdocument generated for the AddressBook JavaBean using JAVA2WSDLaccording to the processes of the present invention for web servicesthat are described as a JavaBean. In FIGS. 12A-12C, the SOAP/HTTPinformation in the binding cannot be used to access the web servicesince the intent is to run the AddressBook JavaBean locally. The WSDLbased internal description shown in FIGS. 12A-12C may be generated as aresult of, for example, step 770 and/or step 810.

FIGS. 13A-13C illustrate the internal service description of FIGS.12A-12C after a Java binding has been added to it. It should be notedthat the “Java” and “format” namespaces have been added to support theJava binding. The internal description shown in FIGS. 13A-13C may begenerated as a result of, for example, step 830.

FIGS. 14A-14C illustrate an original WSDL definition derived from theAddressBook JavaBean of FIG. 11A as might be generated from a differentweb service provider infrastructure such as Apache Axis. As shown inFIGS. 14A-14C, the WSDL definition includes a SOAP/HTTP binding with aport that has a real endpoint address.

FIGS. 15A-15C illustrate the WSDL definition of FIGS. 14A-14C after aJava binding has been added to it. It should be noted that the Javabinding has mappings between the data types defined in the original WSDLdefinition and the Java classes that represent those types for the webservice. This allows the client to use the original WSDL for typemapping, yet allow the web service to use classes known to it torepresent those data types.

During the deployment of a web service in the web services businfrastructure, any type mappings in a binding are described to the buschannel that handles serialization and deserialization. Any incomingrequests have the parameters, with data types named according to theinternal definition of the service, mapped to the correct JavaBeanclasses. The reverse takes place for outgoing responses. With thepresent invention, such operations may be performed whether the targetweb service implementation is initially described with WSDL or not.

In addition, since the present invention allows the creation of internaldefinitions to describe all service implementations either local orremote, the present invention allows consistent use of the bus on-rampto invoke the actual service implementation. Moreover, the ability touse both WSDL and a JavaBean allows client devices to continue to usethe data type name information in the existing WSDL, yet invoke servicesusing the bus supporting a JavaBean as the real implementation. Thepresent invention allows this by creating a description of the serviceusing type name information from the existing WSDL mapped to the actualJava types used by the JavaBean. This requires the client to change onlythe actual endpoint information for the service to invoke the JavaBeandeployed in the bus environment instead of the original environment fromwhich the existing WSDL was derived.

It is important to note that while the present invention has beendescribed in the context of a fully functioning data processing system,those of ordinary skill in the art will appreciate that the processes ofthe present invention are capable of being distributed in the form of acomputer readable medium of instructions and a variety of forms and thatthe present invention applies equally regardless of the particular typeof signal bearing media actually used to carry out the distribution.Examples of computer readable media include recordable-type media such afloppy disc, a hard disk drive, a RAM, and CD-ROMs and transmission-typemedia such as digital and analog communications links.

The description of the present invention has been presented for purposesof illustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the art. Theembodiment was chosen and described in order to best explain theprinciples of the invention, the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

1.-16. (canceled)
 17. A computer program product in a computer readablemedium for deploying a web service, comprising: first instructions forretrieving a deployment descriptor for the web service; secondinstructions for determining a location type for the web service fromthe deployment descriptor; third instructions for deploying the webservice based on the location type for the web service, wherein thedeployment descriptor describes how the web service may be deployed inthe data processing system; and wherein for the location type beingdetermined to indicate that the web service is defined by both aJavaBean and a web services description language (WSDL) document, thethird instructions for deploying the web service include: instructionsfor generating an internal definition of the web service based on theWSDL document; and instructions for adding a Java binding to theinternal definition of the web service, the Java binding correspondingto the JavaBean of the web service.
 18. The computer program product ofclaim 17, wherein the instructions for adding the Java binding include:instructions for performing introspection of the JavaBean to determinedata types used by the JavaBean; and instructions for mapping the datatypes used by the JavaBean to data types defined in the internaldefinition.
 19. The computer program product of claim 17, wherein theinstructions for adding the Java binding include: instructions foradding namespaces for Java extensibility elements; and instructions foradding extensibility elements for mapping to data types used by theJavaBean.
 20. The computer program product of claim 17, wherein addingthe Java binding includes: instructions for removing existing bindingsand service elements in the internal definition; and instructions foradding a service element with a port that references the Java binding.21. The computer program product of claim 17, wherein the instructionsfor adding the Java binding include instructions for adding mappingsbetween data type information obtained from the WSDL document and datatypes used by the JavaBean. 22-23. (canceled)
 24. The computer programproduct of claim 17, wherein the computer program product is transmittedover a communications link.